<?php
/**
 * <https://y.st./>
 * Copyright © 2015 Alex Yst <mailto:copyright@y.st>
 * 
 * This program is free software: you can redistribute it and/or modify
 * it under the terms of the GNU General Public License as published by
 * the Free Software Foundation, either version 3 of the License, or
 * (at your option) any later version.
 * 
 * This program is distributed in the hope that it will be useful,
 * but WITHOUT ANY WARRANTY; without even the implied warranty of
 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
 * GNU General Public License for more details.
 * 
 * You should have received a copy of the GNU General Public License
 * along with this program. Sf not, see <https://www.gnu.org./licenses/>.
**/

$xhtml = array(
	'title' => 'glib is messing up the file-sorting order.',
	'body' => <<<END
<p>
	There is an issue present in the file managers associated with many of the common desktop environments that causes files to be sorted in a bizarre and unintuitive manner.
	Instead of sorting files is such a way that every character is treated as just a character, they are sorted instead treating digits as somehow special.
	All consecutive digits are treated as a single character and sorted from least to greatest.
	This makes it very difficult to find files with names that begin with large strings of digits if the beginning digits are known but the number of digits is not.
	This is far worse than the issue of sorting files case-insensitively.
	With the help of a <a href="https://forum.xfce.org/viewtopic.php?pid=31785#p31785">forum post</a>, I&apos;ve tracked down the problem.
	The problem is glib, which is probably used by most {$a['GTK+']}-based desktops.
	This means that I cannot escape the issue by switching to another desktop, as $a[KDE] is out of the question.
	Furthermore, I can&apos;t find any information on disabling this &quot;feature&quot; in glib.
	When I get the chance, I need to try out some other window managers and see if I can find one that does not have this annoying issue while still being usable.
</p>
<p>
	I tried out a new email client today called Sylpheed.
	It seems alright so far, though does have one issue during setup.
	Sylpheed handles proxies on a per-mail-account basis, so you cannot set up your proxy before setting up your accounts.
	Furthermore, the proxy cannot be set up during the initial setup of a given account.
	Instead, an account must be set up to run over clearnet, then edited to run through the proxy instead.
	To prevent any data leaks, I set the account up to use <code>//localhost.</code> as the mail server, then fixed it to use the real mail server once the proxy was set.
	However, updating the $a[IMAP] and $a[SMTP] servers did not seem to actually allow me to access my mail.
	Eventually I found the problem, which is that Sylpheed does not update the server&apos;s directory tree upon editing the account or upon restarting the email client.
	If you use this method to prevent data leaks over clearnet, you&apos;ll need to tell Sylpheed to refresh the directory tree once the email account settings are in place.
</p>
<p>
	In the $a[CSS] course I&apos;m taking, the professor talked about creating $a[CSS] rules that only apply to hyperlinks to websites that use specific $a[TLD]s.
	The professor&apos;s method does not function outside the toy website we are working with, but it was an interesting concept none the less.
	Specifically, the $a[CSS] selectors she used checked the last few characters of the <code>href</code> attribute to see if they, for example, were &quot;.edu&quot;.
	However, this method requires that no hyperlinks specify a file path.
	At the very least, the <code>/</code> path should be used, but even if a trailing slash was added to the selector, it would not select hyperlinks that used a different path.
	Using a different selector, one could select hyperlinks pointing to $a[URI]s containing &quot;.edu&quot; (or even &quot;.edu/&quot;), but even that would select hyperlinks pointing to $a[URI]s containing this text anywhere in their path, not just those that actually use the &quot;edu.&quot; $a[TLD].
	I&apos;m not sure it is possible to achieve the desired effect without making assumptions that will not always hold true.
	Speaking of $a[CSS], when I have time, I should set my stylesheet to wipe as much of browsers&apos; default style sheets to achieve a more consistent look.
</p>
<p>
	I think that I might move my weblog into onion land.
	My current setup, along with my job hunt, is putting a rift in online identity.
	I don&apos;t want potential employers reading my journal and discriminating against me for its contents, so I&apos;ve had to set up a shallow mask for use only when job hunting.
	But if I torify the personal parts, only people that use Tor or know about the Tor-to-Web gateways will see my more private thoughts.
	I won&apos;t have to be &quot;{legal name}@clovermail.net&quot;, I can be &quot;{legal name}@{my domain}&quot;.
	This applies to more than just email though.
	I plan to get more into software development on my own time, which will of course be released under my real name, not my legal name, using accounts that are tied to my clearnet website.
	With my weblog hosted there, I would have no choice but to hide everything I am behind that shallow mask.
	By moving the personal part of my website to onion land, I insure that most of the people that see it will either be like-minded or technically savvy.
	I will no longer be as much of a blatant target for the nosy.
	When I do this, I&apos;ll use $a[CSS] to hide links to the onion address, then link to a style sheet on the onion that will reveal them.
	It&apos;s not the perfect solution, but it should be pretty decent.
</p>
<p>
	This entry will probably be the last to go live before I set up the onion website and move the weblog to it.
	That means I&apos;m going to have to go dark for a bit, as I do not even have a server machine available right now.
	I&apos;ll spend that time preparing the style sheets and rewriting the links of this website to begin in &quot;//y.st/&quot; or &quot;//quystystxtvdgyst.onion/&quot;, depending on the link.
	I&apos;ll probably continue to update my canary daily and will definitely write weblog entries in the mean time to make available when the onion comes back up.
</p>
<p>
	My <a href="/a/canary.txt">canary</a> still sings the tune of freedom and transparency.
</p>
END
);
